<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Starting a Device</title><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><meta name="keywords" content="Intellon, Atheros, Qualcomm, HomePlug, powerline, communications, INT6000, INT6300, INT6400, AR7400, AR7420"><link rel="home" href="index.html" title="Qualcomm Atheros Open Powerline Toolkit"><link rel="up" href="ch05.html" title="Chapter 5.  Procedures"><link rel="prev" href="ch05s09.html" title="Upgrading PIB Only"><link rel="next" href="ch05s11.html" title="Testing a Device"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">
			Starting a Device
			</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch05s09.html">Prev</a> </td><th width="60%" align="center">Chapter 5. 
		Procedures 
		</th><td width="20%" align="right"> <a accesskey="n" href="ch05s11.html">Next</a></td></tr></table><hr></div><div class="section" title="Starting a Device"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="procedure-initialize-device"></a>
			Starting a Device
			</h2></div></div></div><p>
			Some device configurations have no flash memory to store runtime parameters and firmware so the local host must store them until needed then write them into device <acronym class="acronym">SDRAM</acronym> and start execution. This is also needed when the flash memory is blank or corrupted because the runtime firmware is the only way to write flash memory. Programs <a class="ulink" href="int6kf.7.html" target="_top">int6kf</a>,  <a class="ulink" href="int6kboot.7.html" target="_top">int6kboot</a>, <a class="ulink" href="ampboot.7.html" target="_top">ampboot</a> and <a class="ulink" href="plcboot.7.html" target="_top">plcboot</a> are used to configure a blank device then download runtime parameters and firmware and start execution. They all perform the same basic function but in different ways.
			</p><div class="example"><a name="idp22342000"></a><p class="title"><b>Example 5.18. 
				Start Firmware on <span class="productname">INT6000</span>™
				</b></p><div class="example-contents"><pre class="screen">
# int6kf -C abc.cfg -N abc.nvm -P abc.pib 
</pre><p>
				Program <a class="ulink" href="int6kf.7.html" target="_top">int6kf</a> can be used to download runtime firmware and parameters and start execution on and <span class="productname">INT6000</span>™ chipset. The process involves downloading a <code class="filename">.cfg</code> file using <code class="constant">VS_SET_SDRAM</code>, downloading a <code class="filename">.nvm</code> file using <code class="constant">VS_WR_MEM</code>, downloading a <code class="filename">.pib</code> file using <code class="constant">VS_WR_MEM</code> then starting firmware execution using <code class="constant">VS_ST_MAC</code>. See the <a class="ulink" href="int6kf.7.html" target="_top">int6kf</a> man page for an explanation of the command line options and arguments used here. 
				</p></div></div><br class="example-break"><div class="example"><a name="idp22346720"></a><p class="title"><b>Example 5.19. 
				Start Firmware on <span class="productname">INT6300</span>™ and <span class="productname">INT6400</span>™
				</b></p><div class="example-contents"><pre class="screen">
# int6kboot -N abc.nvm -P abc.pib 
</pre><p>
				Program <a class="ulink" href="int6kboot.7.html" target="_top">int6kboot</a> can be used to download runtime firmware and parameters and start execution on an <span class="productname">INT6300</span>™ or <span class="productname">INT6400</span>™ chipset. The process involves downloading a <code class="filename">.nvm</code> file using <code class="constant">VS_WR_MEM</code>, downloading a <code class="filename">.pib</code> file using <code class="constant">VS_WR_MEM</code> then starting firmware execution using <code class="constant">VS_ST_MAC</code>. No <code class="filename">.cfg</code> file is needed or permitted with this application. 
				</p></div></div><br class="example-break"><div class="example"><a name="idp22351496"></a><p class="title"><b>Example 5.20. 
				Start Firmware on <span class="productname">AR7400</span>™
				</b></p><div class="example-contents"><pre class="screen">
# ampboot -N abc.nvm -P abc.pib 
</pre><p>
				Program <a class="ulink" href="ampboot.7.html" target="_top">ampboot</a> can be used to download runtime firmware and parameters and start execution of runtime firmware on an <span class="productname">INT6300</span>™, <span class="productname">INT6400</span>™ or <span class="productname">AR7400</span>™ chipset. The process involves downloading a <code class="filename">.pib</code> file using <code class="constant">VS_WR_MEM</code>, downloading a <code class="filename">.nvm</code> file using <code class="constant">VS_WR_MEM</code> then starting firmware execution using <code class="constant">VS_ST_MAC</code>. A general purpose applet, stored in the <code class="filename">.nvm</code> file, configures <acronym class="acronym">SDRAM</acronym>. No <code class="filename">.cfg</code> file is needed or permitted with this application. 
				</p></div></div><br class="example-break"><div class="example"><a name="idp22356896"></a><p class="title"><b>Example 5.21. 
				Start Firmware on <span class="productname">AR7420</span>™
				</b></p><div class="example-contents"><pre class="screen">
# plcboot -N abc.nvm -P abc.pib 
</pre><p>
				Program <a class="ulink" href="plcboot.7.html" target="_top">plcboot</a> can be used to download runtime firmware and parameters and start execution an <span class="productname">INT6300</span>™, <span class="productname">INT6400</span>™, <span class="productname">AR7400</span>™ or <span class="productname">AR7420</span>™ chipset. This program detects the type of chipset and the image file format. The boot process varies depending on the chipset that is detected and the image file format. For the <span class="productname">AR7420</span>™ chipset, this process involves downloading a <code class="filename">.pib</code> and <code class="filename">.nvm</code> file using only <code class="constant">VS_WRITE_EXECUTE</code> messages. For earlier chipsets, the process is as described above.
				</p></div></div><br class="example-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch05s09.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch05.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch05s11.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">
			Upgrading PIB Only
			 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 
			Testing a Device
			</td></tr></table></div></body></html>
